<?xml version="1.0" encoding="iso-8859-1"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
<head>
<link href="lagniappe.css" rel="stylesheet" title="Lagniappe Style" type="text/css" />
<title>The Lagniappe Programming Environment</title>
</head>
<body>
<div id="banner">
<img src="lagniappe_logo.png" alt="Lagniappe" />
<h1>The Lagniappe Programming Environment</h1></div>
<div id="wrapper">
<div id="nav2">
<ul>
  <li>Contents
      <ul>
	<li><a href="#intro">Introduction</a></li>
	<li><a href="#news">Project News</a></li>
	<li><a href="#info">Project Information</a></li>
      </ul>
  </li>
  <li>Links
      <ul>
	<li><a
	href="http://code.google.com/p/lagniappe/">Google Project Page</a></li>
	<li><a href="http://code.google.com/p/lagniappe/downloads/list">Downloads</a></li>
	<li><a href="http://www.antlr.org">Antlr</a></li>
      </ul>
  </li>
</ul>
</div>
<div id="maincontent">

<a id="intro"></a><h2>Introduction</h2>

<div style="height:auto;">

<div  style="float:left;width:350px;text-align:justify;">

<p>The emergence of multi-processor, multi-threaded architectures
(referred to as multi-&#8902; architectures) facilitate the design of
high-throughput request processing systems (e.g., programmable
multi-service routers for GENI, intrusion detection systems, graphics
and gaming systems, as well as high-throughput web servers and
transaction processing systems). Because of the challenges in
programming such architectures, however, realizing this promise has
proved to be difficult.</p>

<p>Lagniappe simplifies the design of portable, high-throughput
applications on multi-&#8902; architectures. Lagniappe uses a hybrid
programming model: it combines a procedural specification (e.g.,
in C++) of the basic operators for processing requests with a
declarative specification&#8212;expressed using a model-driven
development framework&#8212;of the various features of the operators and
the target hardware platform. Using the declarative specification, the
Lagniappe programming environment automates the mapping of
applications onto the multi-&#8902; platform, performs dynamic allocation of
resources to operators, and ensures efficient and coherent accesses to
persistent, shared state.</p>

</div>

<img style="height:auto; padding:10px; margin:10px; margin-left:20px;
border:1px solid #000000;" src="SysArchitectureColor.png"
     alt="Lagniappe System Architectre" />

</div>
<div id="bottom">
<a id="news"></a><h2>Project News
<span id="lag-xml"><a href="http://www.cs.utexas.edu/users/riche/lagniappe/atom.xml">
<img src="xml.png" alt="XML Feed" /></a></span></h2>



    
  <h3 class="date-header">Tuesday, April 29, 2008</h3>
  

  
     
  <!-- Begin .post -->
  <div class="post"><a id="l1328381447948966052"></a>
         
    <h4 class="post-title">
	 
	 Busy, busy for OSDI
	 
    </h4>
    

	         <div class="post-body">
	<div class="post">
      <p>Post OSDI I'll update the site on all of the new stuff that has been built into Lagniappe in the last month. It's really coming together, but there is still so much to do before the deadline.</p><p class="blogger-labels">Labels: <a rel='tag' href="http://www.cs.utexas.edu/users/riche/lagniappe/labels/OSDI.html">OSDI</a></p>
    </div>
    </div>
    
    <p class="post-footer">
      <em>posted by Taylor at <a href="http://www.cs.utexas.edu/users/riche/lagniappe/2008/04/busy-busy-for-osdi.html" title="permanent link">10:51 PM</a></em>
        
    </p>
  
  </div>
  <!-- End .post -->
  
  
  
  <!-- Begin #comments -->
 

  <!-- End #comments -->



    
  <h3 class="date-header">Wednesday, April 09, 2008</h3>
  

  
     
  <!-- Begin .post -->
  <div class="post"><a id="l5972785919703143440"></a>
         
    <h4 class="post-title">
	 
	 Big changes
	 
    </h4>
    

	         <div class="post-body">
	<div class="post">
      <p>So I've checked in code (in both the library and compiler) that automatically generates adaptation triggers based on the specifics of the application and system. I did a quick test and it does, in fact, generate different triggers for different hardware platforms, so that was a nice sanity check.</p>

<p>I've also now officially put all of the code under the GPL.</p>

<p>I'm going to spend the next few days on getting some of the paper up-to-date, and then I will start to tackle the smart mapping issue. With those two features on the books, the system will be pretty powerful. We will automatically generate policies to efficiently adapt resources to handle changes in workload based on <span style="font-style:italic;">your specific application and hardware platform</span>. I think that is pretty powerful, but yes, I'm biased.</p><p class="blogger-labels">Labels: <a rel='tag' href="http://www.cs.utexas.edu/users/riche/lagniappe/labels/adaptation.html">adaptation</a>, <a rel='tag' href="http://www.cs.utexas.edu/users/riche/lagniappe/labels/mapping.html">mapping</a>, <a rel='tag' href="http://www.cs.utexas.edu/users/riche/lagniappe/labels/OSDI.html">OSDI</a>, <a rel='tag' href="http://www.cs.utexas.edu/users/riche/lagniappe/labels/writing.html">writing</a></p>
    </div>
    </div>
    
    <p class="post-footer">
      <em>posted by Taylor at <a href="http://www.cs.utexas.edu/users/riche/lagniappe/2008/04/big-changes.html" title="permanent link">2:15 PM</a></em>
        
    </p>
  
  </div>
  <!-- End .post -->
  
  
  
  <!-- Begin #comments -->
 

  <!-- End #comments -->



    
  <h3 class="date-header">Tuesday, March 11, 2008</h3>
  

  
     
  <!-- Begin .post -->
  <div class="post"><a id="l4682446931304666465"></a>
         
    <h4 class="post-title">
	 
	 Update
	 
    </h4>
    

	         <div class="post-body">
	<div class="post">
      <p>Things are starting to gel in my head and I'm starting a long section of implementation. Many features to get up and running and tested. Testing is something that I'm actually going to have to put some thought in. It is easy to test particular features in isolation, but the real trick in this work is watching the system deal with large-scale changes in incoming traffic. Generating the traffic that will properly trigger this activity and model real-life traces will be challenging.</p>

<p>The machines are here and installed in the machine room. They should be completely functional soon.</p>

<p>I will try to discuss the implementation as I go along.</p><p class="blogger-labels">Labels: <a rel='tag' href="http://www.cs.utexas.edu/users/riche/lagniappe/labels/new hardware.html">new hardware</a>, <a rel='tag' href="http://www.cs.utexas.edu/users/riche/lagniappe/labels/OSDI.html">OSDI</a>, <a rel='tag' href="http://www.cs.utexas.edu/users/riche/lagniappe/labels/traces.html">traces</a></p>
    </div>
    </div>
    
    <p class="post-footer">
      <em>posted by Taylor at <a href="http://www.cs.utexas.edu/users/riche/lagniappe/2008/03/update.html" title="permanent link">12:09 PM</a></em>
        
    </p>
  
  </div>
  <!-- End .post -->
  
  
  
  <!-- Begin #comments -->
 

  <!-- End #comments -->



    
  <h3 class="date-header">Thursday, February 07, 2008</h3>
  

  
     
  <!-- Begin .post -->
  <div class="post"><a id="l793203068166898569"></a>
         
    <h4 class="post-title">
	 
	 So where are we?
	 
    </h4>
    

	         <div class="post-body">
	<div class="post">
      <p>The Lagniappe project is embarking on very busy few months. With the OSDI deadline in early May, and my graduation in August, there is much work to be done.</p>

<p>There are now two other members on the Lagniappe team. Aruna and Rohan are helping me this semester. We are looking at many different avenues for showing Lagniappe's effectiveness.</p>

<p>We have some new hardware coming in that I am very excited about. We will have 32 cores to play with and these machines will allow us to really validate our ideas on a powerful, working system.</p>

<p>I am in the process of updating the Lagniappe web presence. I want to make sure that everything is correct, accurate, and up-to-date.</p>

<p>Wish us luck!</p><p class="blogger-labels">Labels: <a rel='tag' href="http://www.cs.utexas.edu/users/riche/lagniappe/labels/Lagniappe team.html">Lagniappe team</a>, <a rel='tag' href="http://www.cs.utexas.edu/users/riche/lagniappe/labels/webpage.html">webpage</a></p>
    </div>
    </div>
    
    <p class="post-footer">
      <em>posted by Taylor at <a href="http://www.cs.utexas.edu/users/riche/lagniappe/2008/02/so-where-are-we.html" title="permanent link">12:28 PM</a></em>
        
    </p>
  
  </div>
  <!-- End .post -->
  
  
  
  <!-- Begin #comments -->
 

  <!-- End #comments -->



    
  <h3 class="date-header">Wednesday, January 02, 2008</h3>
  

  
     
  <!-- Begin .post -->
  <div class="post"><a id="l2553318905220139919"></a>
         
    <h4 class="post-title">
	 
	 Proposal Time
	 
    </h4>
    

	         <div class="post-body">
	<div class="post">
      <p>I am in the process of working on the presentation for my dissertation proposal. After that, I will get the updated goals and features up on the site as we start the final push to get Lagniappe full functional ahead of OSDI.</p><p class="blogger-labels">Labels: <a rel='tag' href="http://www.cs.utexas.edu/users/riche/lagniappe/labels/proposal.html">proposal</a></p>
    </div>
    </div>
    
    <p class="post-footer">
      <em>posted by Taylor at <a href="http://www.cs.utexas.edu/users/riche/lagniappe/2008/01/proposal-time.html" title="permanent link">2:52 PM</a></em>
        
    </p>
  
  </div>
  <!-- End .post -->
  
  
  
  <!-- Begin #comments -->
 

  <!-- End #comments -->



<a id="info"></a><h2>Project Information</h2>

<p>
The Lagniappe project is currently hosted by
<a
href="http://code.google.com/hosting/">Google Code</a>. The
project is in the early stages of development. File releases,
project news, and information can all be found at the <a
href="http://code.google.com/p/lagniappe/">project page</a>.
</p>

<h3>Implementation Details</h3>

<p>There are two major components of the Lagniappe Programming
Environment. The first, the Lagniappe Language Translator is written
using Antlr and Java. The second component, the Lagniappe Execution
Environment, is written in C++.</p>
      
<h3>Credits and Web Details</h3>

<p>The Lagniappe project is brought to you by <a
href="http://www.cs.utexas.edu/users/riche/">Taylor
L. Rich&eacute;</a> under the watchful eyes of professors <a
href="http://www.cs.utexas.edu/users/vin/">Harrick M. Vin</a> and <a
href="http://www.cs.utexas.edu/users/lavender/">Greg Lavender</a> from
within the <a href="http://www.cs.utexas.edu/lasr/">Laboratory for
Advanced Systems Research</a> in the <a
href="http://www.cs.utexas.edu/">Department of Computer Sciences</a>
at the <a href="http://www.utexas.edu/">University of Texas at
Austin</a>.</p>

<h4>Project Funding</h4>

<p>We would like to thank the <a href="http://www.nsf.gov">NSF</a>,
the <a href="http://www.arpatp.com/">Texas ARP/ATP</a>, and <a
href="http://www.intel.com">Intel Corporation</a> for their funding of
this work.</p>
      
<h4>Project hosting</h4>

<p>Project hosting provided by <a href="http://code.google.com/hosting/">Google Code</a>.</p>

<p>Weblogging framework provided by <a href="http://www.blogger.com">Blogger</a>.</p>

<h4>Page validation</h4>

<p>We support web standards. This page is written in XHTML 1.1 using
CSS. The following validate the page using the w3's validation
services.</p>

<p>

<a href="http://validator.w3.org/check?uri=referer"> <img
style="border:0;width:88px;height:31px"
src="http://www.w3.org/Icons/valid-xhtml11-blue" alt="Valid XHTML 1.1!" />
</a>

<a href="http://jigsaw.w3.org/css-validator/check/referer"> <img
style="border:0;width:88px;height:31px"
src="http://jigsaw.w3.org/css-validator/images/vcss" alt="Valid CSS!"
/>
</a>

</p>
</div>
</div>
</div>
</body>

</html>
